Systems and methods for rewards engagement score

ABSTRACT

Systems, methods, and apparatuses for encouraging engagement with a rewards system are described herein. A customer associated with a customer device holds a rewards account with a provider associated with a provider computing system. The provider computing system receives rewards and payment card activity of the customer, analyzes the rewards and payment card activity, and generates a rewards engagement rating, which the provider uses to generate and transmit tailored rewards engagement messages to the customer device. The messages provide rewards earn and burn opportunities in which the customer can select to participate.

TECHNICAL FIELD

Embodiments of the present disclosure relate to systems and methods forrewards engagement.

BACKGROUND

Many issuers of credit cards offer rewards points to customers. Forexample, some credit card issuers provide one reward point for everydollar spent on the credit card. Accordingly, as a customer continues touse a rewards credit card, the customer accumulates rewards points. Thecustomer can then redeem the rewards points. Some customers may forgetthat the rewards points are available to them. Some customers may alsonot effectively use their payment cards to earn points up to theirpotential.

SUMMARY

A first example embodiment relates to a method of encouraging rewardsactivity. The method includes receiving, by a provider computing systemassociated with a provider, rewards activity information associated witha rewards account maintained by the provider and associated with thecustomer, receiving payment card information associated with the paymentaccount, generating a rewards engagement score based on the rewardsactivity information and the payment card information, generating arewards engagement message, and transmitting the rewards engagementmessage to a customer device associated with the customer.

Another example embodiment relates to a provider computing systemassociated with a provider. The provider computing system includes anetwork interface structured to facilitate data communication via anetwork, an accounts database structured to store information associatedwith a payment account associated with a customer, a rewards databasestructured to store information associated with a rewards accountassociated with the customer, and a processing circuit comprising aprocessor and memory. The processing circuit is structured to receiverewards activity information associated with the rewards accountmaintained by the provider and associated with the customer, receivepayment card information associated with the payment account, generate arewards engagement score based on the rewards activity information andthe payment card information, generate a rewards engagement messagebased on the rewards engagement score, and transmit the rewardsengagement message to a customer device associated with the customer.

Another example embodiment includes a customer device. The customerdevice includes a network circuit structured to communicate data to andfrom a provider computing system associated with a provider of a rewardsaccount associated with the customer, an input/output device structuredto exchange data with the customer, and a processing circuit comprisinga processor and memory. The processing circuit is structured to receive,by the network circuit, a first graphical interface from the providercomputing system, where the first graphical interface identifies one ormore rewards account held by the customer at the provider and one ormore rewards engagement messages generated by the provider computingsystem in response to customer engagement with the one or more rewardsaccounts, and where the first graphical interface further enables thecustomer to select the one or more rewards engagement messages. Theprocessing circuit is further structured to receive a first input fromthe customer via the input/output device, the first input indicating auser selection of one of the one or more rewards engagement messages,and transmit, via the network circuit, the customer selection, to theprovider computing system.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a view of a rewards engagement system according to an exampleembodiment.

FIG. 2 is a view of a flow diagram of a method of engaging the customerthrough the rewards system according to an example embodiment.

FIG. 3 is a view of a flow diagram of a method of engaging the customerthrough the rewards system according to an example embodiment.

FIGS. 4 through 8 show various user interfaces of a customer deviceimplementing the rewards engagement system as described in the method ofFIGS. 2-3.

DETAILED DESCRIPTION

Referring to the figures generally, systems, methods, and apparatusesfor encouraging rewards system engagement are described herein. Acustomer of a provider having a rewards account may not be utilizing therewards account to the full potential as determined by the provider ofthe rewards account. For example, the customer may not be effectivelyearning rewards points based on their transaction history (e.g.,customer is using a debit card for purchases instead of a credit card).By analyzing the customer's transaction history, rewards pointsredemption history, the customer's rewards points preferences, etc., theprovider identifies opportunities for the customer to earn or burnrewards points (e.g., redeem points, pay with points) and presents theseopportunities to the customer in various forms.

To identify such opportunities, the provider generates a rewardsengagement score for the customer, which is indicative of the customer'spast engagement activities with the rewards system. The rewardsengagement score is determined using the past earning activity and thepast burning activity, such as paying with rewards points, redemption ofrewards points, etc. As noted, using the rewards engagement score, theprovider identifies opportunities for the customer to earn or burnrewards points and presents these opportunities to the customer invarious forms. In some arrangements, the provider provides theopportunities in the form of an advertisement or banner presented on awebsite of the provider, an advertisement or banner on a clientapplication of the customer device, a push notification to the customerdevice, etc. In some arrangements, the provider also determines one ormore channels through which to present the opportunities (e.g., via aclient application, via an online provider portal, etc.).

As used herein, “points” refers to rewards issued by a provider to acustomer that can be redeemed through the provider and/or exchanged intocurrency by the provider at an exchange rate that is defined by theprovider. As used herein, to “earn” or “earning” points refers to, butis not limited to, the act of receiving rewards points in exchange for apayment made by the customer using the payment card linked to therewards account, signing up for a particular payment card, acceptingpromotional offers such as multiplied points, accepting offers from theprovider to participate in certain programs provided by the provider,and the like. As used herein, to “burn” or “burning” points refers to,but is not limited to, using rewards points to make a purchase,redeeming rewards points for items or services, transferring rewardspoints to other customers, etc.

An example embodiment is described as follows. A customer holds arewards account connected to a payment card (e.g., a credit cardaccount, a debit card account) associated with a provider. The rewardsaccount is structured such that the customer earns a rewards balance(e.g., rewards points, cashback rewards) in the customer's rewardsaccount by using the payment account. For example, the customer earnsone rewards point per dollar the customer spends using the paymentaccount. In some cases, the customer may not be fully utilizing therewards account such that they are not earning and using points in a wayin which the rewards account is providing the optimal benefit to thecustomer.

The system described herein generates a customer-specific advertisementor banner based on the customer's rewards engagement score, which thesystem displays to the customer (e.g., as a rewards ad shown as part ofa provider website, push notification to a customer device, as anotification on a client application, etc.). More specifically, if thesystem determines that the customer is either not earning or burningtheir rewards points in a manner which is optimally benefitting thecustomer and/or is relatively less than an average customer, the systemgenerates and displays an ad or banner informing the customer ofopportunities to earn or burn rewards points. The customer can click onthe banner, and in response, the system redirects the customer to ascreen relating to the rewards opportunity. For example, the screenshows the customer additional information about the ways in which thecustomer can burn rewards points, such as paying for a trip with rewardspoints, redeeming rewards points for cash, etc. As another example, thescreen shows the customer additional information about the ways in whichthe customer can earn rewards points, such as using a certain creditcard for purchases which may provide a higher rate of rewards pointsthan a debit card, etc. In some arrangements, the customer can beredirected to a particular merchant site to make a purchase usingrewards points, etc.

The systems and methods described herein offer advantages for a customerhaving a rewards account with a provider. Many customers unknowinglyallow their rewards balances to become stagnant, where rewards pointsmay even expire without the customer redeeming them, causing thecustomer to have negative experiences with the rewards system. This, inturn, can decrease the customer's engagement with the customer's paymentaccount, which is detrimental to the provider of the payment account. Assuch, generating notifications to customers with earning and burningopportunities based on their past engagement history may help customersto become more engaged with the rewards system. As a result, customersmay have more positive experiences with the rewards system and remainlonger, better customers of the provider. Furthermore, when thecustomers become more engaged with the rewards system, fewer and fewerreminders for earn and burn opportunities need to be generated andmessaged to the customer, thereby reducing the necessary activity forthe provider computing systems.

Referring to FIG. 1, a view of a rewards engagement system 100 is shownaccording to an example embodiment. Generally, the system 100facilitates the promotion of a customer's engagement with a providedrewards account. The rewards engagement system 100 includes a customerdevice 112 and a provider computing system 118. In some arrangements,the rewards engagement system 100 also includes merchant points ofpurchase, such as the merchant POS terminal 114 and a merchant eCommercehost 116, where a customer can complete purchases to earn reward pointsand/or where a customer can make purchases using points (e.g., burnrewards points).

The rewards account of the customer is maintained by the provider. Insome arrangements, the rewards account is associated with a paymentaccount (e.g., a credit account, a line of credit, a demand depositaccount, a prepaid account, etc.) maintained by the provider. In sucharrangements, the customer may accrue points in the rewards account bypaying for purchases from the payment account. For example, the paymentaccount may be a credit account in which the customer earns a certainnumber of points for every dollar spent with the credit account (e.g.,one point for one dollar, two points for one dollar, a certainpercentage of the amount of purchases made, etc.). Through the system,the customer can pay for purchases with the payment account through anynumber of channels, including a payment card 108, a mobile wallet client146 running on a mobile device (e.g., a smartphone) associated with thecustomer, or by providing payment account information to the merchant(e.g., via the payment card 108, via a customer device 112, by providingpayment account information to a representative in person or over thephone, by entering payment account information into a website, etc.).

The provider (or provider computing system 118) can provide variousversions of rewards. Examples of rewards include rewards points, cashrewards, travel or hotel rewards, gas rewards, and so on. Additionally,the customer redeems earned rewards for various rewards items. Forexample, in some embodiments, a customer redeems earned rewards byexchanging them for physical or digital goods or services. As anillustration, a customer redeems a certain number of rewards points foran airline ticket or a gift card. In other embodiments, a customerredeems earned rewards for cash or a cash balance. For example, acustomer's rewards are reflected as a cashback bonus that the customercan apply as a statement credit, receive as a check, receive as a giftcard, receive as cash, and so on.

Additionally, rewards are earned in different ways according todifferent embodiments. In one embodiment, spending a certain amount ofmoney earns the customer a certain amount of rewards. For example,spending a dollar earns the customer one rewards point. As anotherexample, spending a dollar earns the customer two cents in cashbackrewards. In another embodiment, the customer earns more rewards bymaking certain purchases or by making purchases at certain retailers orbusinesses. In one example, the customer generally earns one rewardspoint per dollar spent on most goods and services but earns three pointsper dollar spent at gas stations. In another example, the customer earns2% cashback on grocery purchases and 3% cashback on travel purchases. Insome implementations, the customer earns additional rewards based onrotating categories. For example, in the first quarter, the customerearns 4% extra in cashback rewards on restaurant purchases, and thecustomer earns 4% extra in cashback rewards on gas purchases in thesecond quarter. In yet another embodiment, the customer alternatively oradditionally earns rewards by performing certain actions. As an example,the customer earns an extra 1% in cashback rewards by paying off thecustomer's credit card balance in full by the customer's monthly paymentdeadline.

Still referring to FIG. 1, the customer device 112 includes a networkinterface 140 enabling the customer device 112 to exchange informationover the network 122, an input/output circuit 142, a display 144, amobile wallet client 146, and a client application 148. The networkinterface 140 is used to establish connections via the network 122between the customer device 122 and other devices or computing systems.The network 122 further supports communication between the customerdevice 112 and other devices or computing systems. The customer device112 also includes a processor and a memory similarly configured as thatof the provider computing system 118 described below. The memory mayinclude non-transitory storage mediums housing one or more logics thatinclude instructions executable by the processor so as to configure thecustomer device 112 to exchange data over the network 122, executesoftware applications, access websites, generate graphical userinterfaces, and perform other similar operations.

The input/output circuit 142 is structured to receive communicationsfrom and provide communications to the customer associated with thecustomer device 112. In this regard, the input/output circuit 142 isstructured to exchange data, communications, instructions, etc. with aninput/output component of the customer device 112. Accordingly, in oneembodiment, the input/output circuit 142 includes an input/outputdevice. In another embodiment, the input/output circuit 142 includescommunication circuitry for facilitating the exchange of data, values,messages, and the like between an input/output device and the componentsof the customer device 112. In yet another embodiment, the input/outputcircuit 142 includes machine-readable media for facilitating theexchange of information between an input/output device and thecomponents of the customer device 112. In still another embodiment, theinput/output circuit 142 includes any combination of hardwarecomponents, communication circuitry, and machine-readable media.

In various embodiments, the display 144 is a screen, a touchscreen, etc.In some arrangements, the customer device 112 uses the display 144 tocommunicate information to the user, for example, by displayinginformation to the customer on the display 144. In some arrangements,the customer device 112 additionally uses the display 144 to receivecommunications from the user, for example, through a keyboard providedon a touchscreen of the display 144. Accordingly, in certainarrangements, the display 144 is incorporated as an input/output deviceassociated with the input/output circuit 142.

The client application 148 is structured to provide displays to thecustomer device 112 that enable the customer to manage interactions withthe rewards engagement system 100 and may be used to manage accountsheld with the provider. Accordingly, the client application 148 iscommunicably coupled to the provider computing system 118 (e.g., theengagement rating circuit 130, messaging circuit 132, etc.). In someembodiments, the client application 148 may be incorporated with anexisting application in use by the provider (e.g., a mobile bankingapplication or a mobile wallet application). In other embodiments, theclient application 148 is a separate software application implemented onthe customer device 112. The client application 148 may be downloaded bythe customer device 112 prior to its usage, hard coded into the memoryof the customer device 112, or be a web-based interface application suchthat the customer device 112 may provide a web browser to theapplication, which may be executed remotely from the customer device112. In the latter instance, the user may have to log onto or access theweb-based interface before usage of the applications. Further, and inthis regard, the client application 148 may be supported by a separatecomputing system including one or more servers, processors, networkinterface circuits, etc. that transmit applications for use to thecustomer device 112. In certain embodiments, the client application 148includes an API and/or a software development kit (SDK) that facilitatethe integration of other applications with the client application 148.For example, the client application 148 may include an API thatfacilitates the receipt of information pertaining to the rewardsengagement system 100 as described further below.

The displays presented to the user via the client application 148 may beindicative of rewards engagement information, rewards earnopportunities, rewards burn opportunities, current account balances,pending transactions, profile information (e.g., contact information),and the like. The client application 148 may also provide a prompt tothe customer to submit preferences to the system 100. For example, insome arrangements, the client application 148 may prompt the customerwhether they desire to receive earn or burn opportunities, what types ofearn or burn opportunities they would like to be informed of in thefuture, the types of channels through which they would like to receivemessages from the system 100.

The payment card 108 is a physical card, such as a credit card, a debitcard, a prepaid card, or the like. Accordingly, the payment card 108 canprovide account information associated with the payment account (e.g.,account number, expiration date, etc.) to a merchant point of sale(“POS”) terminal 114 during a transaction between the merchant and thecustomer. The account information may be transmitted, for example,through an encoded magnetic stripe, an embedded smart chip (e.g., an EMVchip), through an embedded near-field communication (“NFC”) tag, QRcode, or the like. For example, the customer can swipe, insert, scan, ortap the payment card 108 at the merchant POS terminal 114 during anin-person transaction at a location of the merchant.

The mobile wallet client 146 is an application executed by a mobiledevice (e.g., a smartphone) associated with the customer. The mobilewallet client 146 is structured to provide payment account informationto the merchant POS terminal 114 (e.g., by presenting a payment code ona display of the mobile device, by transmitting payment accountinformation via a Bluetooth or NFC transmission, etc.). In somearrangements, the mobile wallet client 110 may be any of Apple® Pay,Android® Pay, Samsung® Pay, Wells Fargo® Wallet, or the like.

The customer can also provide the payment account information to aneCommerce host 116 associated with the merchant 104 during an onlinetransaction. For example, the customer 102 can access the onlineshopping website associated with the merchant 104 via the customercomputing device 112 and provide payment account information through acheckout feature of the online shopping web site. In some arrangements,the payment account information corresponds to an account number andexpiration date printed or displayed on the payment card 108. Thepayment account information may, for example, be input into the customercomputing device 112 by the customer 102 by typing the payment cardinformation in or by transmitting the payment account information fromthe payment card 108 to the customer computing device 112. In analternate arrangement, the payment account information can be providedvia transmission from the mobile wallet client 110 to the eCommerce host116. In a further arrangement, the payment account information can beprovided over the phone to a representative of the merchant 104 andassociated with a transaction facilitated with the eCommerce host 116.

Still referring to FIG. 1, the payment account is maintained by theprovider. The provider may be, for example, a credit card issuer, abank, or the like. The provider manages a provider computing system 118.The provider computing system 118 includes a network interface 120. Thenetwork interface 120 is used to establish connections with othercomputing systems by way of a network 122. The network 122 may includeany combination of the internet, a private banking network, and thelike. The network interface 120 includes program logic that facilitatesconnection of the financial institution computing system 118 to thenetwork 122. For example, the network interface 120 may include anycombination of a wireless network transceiver (e.g., a cellular modem, aBluetooth transceiver, a WiFi transceiver, etc.) and/or a wired networktransceiver (e.g., an Ethernet transceiver). In some arrangements, thenetwork interface 120 includes the hardware and machine-readable mediasufficient to support communication over multiple channels of datacommunication. Further, in some arrangements, the network interface 120includes cryptography capabilities to establish a secure or relativelysecure communication session in which data communicated over the sessionis encrypted.

The provider computing system 118 includes a processing circuit 124having a processor 126 and memory 128. The processor 126 may beimplemented as a general-purpose processor, an application specificintegrated circuit (ASIC), one or more field programmable gate arrays(FPGAs), a digital signal processor (DSP), a group of processingcomponents, or other suitable electronic processing components. Thememory 128 includes one or more memory devices (e.g., RAM, NVRAM, ROM,Flash Memory, hard disk storage, etc.) that store data and/or computercode for facilitating the various processes described herein. Moreover,the memory 128 may be or include tangible, non-transient volatile memoryor non-volatile memory.

The provider computing system 118 includes an engagement rating circuit130 and a messaging circuit 132. Although FIG. 1 shows the engagementrating circuit 130 and the messaging circuit 132 as part of theprocessing circuit 124, in other arrangements one of or both of theengagement rating circuit 130 and/or the messaging circuit 132 areembodied as separate processing circuits. Other arrangements may includemore or less circuits without departing from the spirit and scope of thepresent disclosure. Further, some arrangements may combine theactivities of one circuit with another circuit to form a single circuit.Therefore, those of ordinary skill in the art will appreciate that thepresent arrangement is not meant to be limiting.

The engagement rating circuit 130 is configured to receive variouscustomer rewards activity and customer payment card activity, analyzethe nature of the activity in relation to the engagement of the customerwith the rewards system 100, and generate a rewards engagement score orrating indicative of the customer's engagement with the rewards system100. In some arrangements, the rewards activity information is receivedfrom the customer device 112 (e.g., through an online banking website,via the client application 148, via the mobile wallet client 146).Accordingly, the engagement rating circuit 130 is communicably andoperatively coupled to the customer device 112.

The rewards activity information relates to the interactions thecustomer has with various aspects of the rewards system 100. Forexample, the customer may visit a website of the provider to access arewards store where the customer views various items or services forwhich the customer can redeem rewards points. In some arrangements,rewards activity can also include, for example, the number of times acustomer has visited a webpage to view reward travel options, the numberof times the customer has redeemed rewards points for travel, etc.

In some arrangements, the payment card activity information is receivedfrom the customer device 112 (e.g., mobile wallet client 146, clientapplication 148). In this case, the customer may have completed apurchase using the payment card 108 via the mobile wallet client 146 ata merchant POS terminal 114 or may have completed a purchase online atan eCommerce host 116 of a merchant. In some arrangements, the paymentcard activity information may also be received from the merchant as orimmediately after the transaction between the customer and the merchantis completed.

The engagement rating circuit 130 analyzes the activity of the customerin relation to the rewards system. The engagement rating circuit 130determines how the rewards and payment activity relate to the customer'sengagement with the rewards system 100. The engagement rating circuit130 can weigh specific rewards and/or payment card activity informationdepending on the activity's relation to an indication that the customeris engaged with the rewards account. For example, the engagement ratingcircuit 130 may weigh a trip purchase using rewards points higher than aredemption of points for cash. As another example, the engagement ratingcircuit 130 may weigh payment card activity information higher thanrewards activity information, and so on.

Based on the analysis of the customer rewards and payment card activity,the engagement rating circuit 130 generates a rewards engagement scorefor each customer. The rewards engagement score is indicative of howengaged the customer is with the rewards account. For example, a higherrewards engagement score may be indicative of a highly engaged customerand a lower rewards engagement score may be indicative of a less engagedcustomer. The rewards engagement score may be made up of a series ofmetrics relating to both the reward activity and the payment cardactivity of the customer.

As an example, the rewards engagement score may range from 0-100 points,where half of the points (e.g., 50 points) are made up of metricsrelating to the reward activity, such as frequency of rewardsredemptions, frequency of rewards store visits, use of other providerproducts, and various program loyalty earn activity. The other half ofthe points (e.g., 50 points) are made up of metrics relative to thepayment card activity, such as average point-of-sale spend during thepast year, number of “everyday spend” categories (e.g., groceries,restaurants, gas, entertainment, etc.), digital wallet usage (e.g.,usage of mobile wallet client 150), number of months with a minimumspend of $50, and so on.

The engagement rating circuit 130 is also configured to receive furtherinteraction indications from the customer received at the customerdevice 112 and analyze the further interaction indications to generatean updated rewards engagement score. Further interaction indications maybe the actions the customer takes in response to messages ornotifications the system 100 sends to the customer. In somearrangements, the interaction indication is an interaction the customerhad with the previously transmitted rewards engagement message. Theinteraction can include, but is not limited to, a dismissal of themessage, clicking on a link in the message to view earn and burnopportunities, clicking on a link in the message to view aninformational video, clicking on a link in the message to chat with aprovider representative, etc. The engagement rating circuit 130 analyzesthe activity and determines what type of interaction the customer hadwith the previously sent rewards engagement message.

Depending on the type of interaction, the rewards engagement score maygo up or down. For example, if the customer interacted with the systemto dismiss the previous rewards engagement message, the rewardsengagement score will likely be a lower rewards engagement score thanpreviously given to the customer due to the dismissal of the message. Asanother example, if the customer interacted with the system to click ona link in the message to view further information about how to earn orburn more rewards points, the rewards engagement score will likely be ahigher rewards engagement score than previously given to the customerdue to the customer's engagement with the system.

The messaging circuit 132 is configured to receive the rewardsengagement score from the engagement rating circuit 130, determine thetype of message to send to the customer, and transmit the message.Accordingly, the messaging circuit 132 is communicably and operativelyto the engagement rating circuit 130 and the customer device 112. Themessaging circuit 132 receives the rewards engagement score from theengagement rating circuit 130 and determines the type of message to sendto the customer. In some arrangements, the messaging circuit 132 is alsoconfigured to receive an updated rewards engagement score from theengagement rating circuit 130 and determine the type of updated messageto send to the customer. For example, the messaging circuit 132 maydetermine that the most effective message to the customer would be abanner displayed on a website of the provider, where for example, thecustomer views payment account and rewards account balances. The bannermay prompt the customer to take an action relating to their rewardsaccount. The banner may include a selectable link such that the customercan take various actions by selecting on the link in the banner, suchas, making a purchase using rewards points at a merchant by clicking onthe link displayed in the banner.

The rewards engagement message is transmitted to the customer in variousways. In some arrangements, the rewards engagement message can betransmitted to the customer as a push notification on the customerdevice 112. In some arrangements, the rewards engagement message can betransmitted to the customer as an advertisement provided on the clientapplication 148. The way in which the message is transmitted to thecustomer can also be determined by the messaging circuit 132. Themessaging circuit 132 can retrieve stored customer preferences, whichmay indicate through which channels the customer prefers to receive earnand burn opportunity messages. As such, the messaging circuit 132 iscommunicably and operatively coupled to the rewards account database136. In some arrangements, the messaging circuit 132 transmits therewards engagement message using the previous channel through which amessage was sent. In this way, the messaging circuit 132 is targetingthe message to the customer in a way that the customer has been promptedto interact with previously and as such, is likely to get the customerto interact with again.

The provider computing system 118 includes the accounts database 134. Insome arrangements, the memory 128 includes the accounts database 134. Inother arrangements, the accounts database 134 is a separate data storagedevice from the memory 128. The accounts database 134 is configured toretrievably hold, store, categorize, and otherwise serve as a repositoryfor information associated with accounts (e.g., loan accounts, savingsaccounts, checking accounts, credit accounts, etc.) held by theprovider. For example, the accounts database 134 may store accountnumbers, account balances, account ownership information, and the like.The accounts database 134 is structured to selectively provide access toinformation relating to an account at the provider.

The provider computing system 118 also includes the rewards database136. In some arrangements, the memory 128 includes the rewards database136. In other arrangements, the rewards database 136 is a separate datastorage device from the memory 128. The rewards database 136 isconfigured to retrievably hold, store, categorize, and otherwise serveas a repository for information associated with rewards accounts held byvarious customers of the provider associated with the provider computingsystem 118. The information stored in the rewards database 136 includes,for example, rewards balances for various customer, what the customercan redeem rewards for, past rewards earn and burn activities, timing ofpast rewards earn and burn activities, potential opportunities forrewards earn and burn activities, and so on.

Referring to FIG. 2, a flow diagram of a method 200 of engaging thecustomer through the rewards system is shown according to an exampleembodiment. The method 200 is performed by the provider computing system118. Through the method 200, the provider computing system 118 generatesa rewards engagement score or rating for customers and uses that ratingto provide tailored earn and burn opportunities to the customers,thereby informing the customer the ways in which the customer can bemore engaged with the rewards system 100.

The method 200 begins when rewards activity information is received at202. The rewards activity information is received at the providercomputing system 118. The rewards activity information may be receivedfrom the customer device 112 (e.g., through an online banking website,via the client application 148, via the mobile wallet client 146). Therewards activity information relates to the interactions the customerhas with various aspects of the rewards system 100. For example, thecustomer may visit a website of the provider to access a rewards storewhere the customer views various items or services for which thecustomer can redeem rewards points. In some arrangements, rewardsactivity can also include, for example, the number of times a customerhas visited a webpage to view reward travel options, the number of timesthe customer has redeemed rewards points for travel, etc.

Payment card activity is received at 204. The payment card activity isreceived at the provider computing system 118. In some arrangements, thepayment card information is received from the customer device 112 (e.g.,mobile wallet client 146, client application 148). In this case, thecustomer may have completed a purchase using the payment card 108 viathe mobile wallet client 146 at a merchant POS terminal 114 or may havecompleted a purchase online at an eCommerce host 116 of a merchant. Insome arrangements, the payment card information may also be receivedfrom the merchant as or immediately after the transaction between thecustomer and the merchant is completed.

The rewards and payment card activity information is analyzed at 206. Insome arrangements, the reward and payment card activity information isanalyzed by the engagement rating circuit 130 of the provider computingsystem 118. The engagement rating circuit 130, as noted above, analyzesthe activity of the customer in relation to the rewards system. Theengagement rating circuit 130 can weight specific rewards and/or paymentcard activity information depending on the activity's relation to anindication that the customer is engaged with the rewards account. Forexample, the engagement rating circuit 130 may weigh a trip purchaseusing rewards points higher than a redemption of points for cash. Asanother example, the engagement rating circuit 130 may weigh paymentcard activity information higher than rewards activity information, andso on.

A rewards engagement score is generated based on the rewards and paymentcard activity information at 208. In some arrangements, the rewardsengagement score is generated by the engagement rating circuit 130 ofthe provider computing system 118. Based on the analysis performed at206, the engagement rating circuit 130 generates a rewards engagementscore for each customer. The rewards engagement score is indicative ofhow engaged the customer is with the rewards account. For example, ahigher rewards engagement score may be indicative of a highly engagedcustomer and a lower rewards engagement score may be indicative of aless engaged customer.

A rewards engagement message is generated at 210. In some arrangements,the rewards engagement message is generated by the messaging circuit 132of the provider computing system 118. The messaging circuit 132 receivesthe rewards engagement score from the engagement rating circuit 130 anddetermines the type of message to send to the customer. For example, themessaging circuit 132 may determine that the most effective message tothe customer would be a banner displayed on a website of the provider,where for example, the customer views payment account and rewardsaccount balances. The banner may prompt the customer to take an actionrelating to their rewards account. The banner may include a selectablelink such that the customer can take various actions by selecting on thelink in the banner, such as, making a purchase using rewards points at amerchant by clicking on the link displayed in the banner.

The rewards engagement message is transmitted to the customer at 212.The rewards engagement message is transmitted to the customer in variousways. In some arrangements, the rewards engagement message can betransmitted to the customer as a push notification on the customerdevice 112. In some arrangements, the rewards engagement message can betransmitted to the customer as an advertisement provided on the clientapplication 148. The way in which the message is transmitted to thecustomer can also be determined by the messaging circuit 132. Themessaging circuit 132 can retrieve stored customer preferences, whichmay indicate through which channels the customer prefers to receive earnand burn opportunity messages.

Referring to FIG. 3, a flow diagram of a method 300 of engaging thecustomer through the rewards system is shown according to an exampleembodiment. The method 300 is performed by the provider computing system118. Through the method 300, the provider computing system 118 continuesto monitor the rewards and payment card activity of the customer andupdates a rewards engagement score or rating for the customer.

The method 300 begins when an interaction indication is received fromthe customer at 302. The interaction indication is received by theprovider computing system 118. The interaction indication is aninteraction the customer had with the previously transmitted rewardsengagement message (e.g., at step 212 above). The interaction caninclude, but is not limited to, a dismissal of the message, clicking ona link in the message to view earn and burn opportunities, redeemingrewards points for items or services, paying for merchandise or serviceswith rewards points, clicking on a link in the message to view aninformational video, clicking on a link in the message to chat with aprovider representative, etc. In some arrangements, the interactionindication is received when the customer redeems the rewards points foritems or services. In this case, the system 100 is also capable ofdebiting the corresponding amount of rewards points from the customer'srewards account balance. In some arrangements, the interactionindication is received when the customer makes a purchase using rewardspoints. In this case, the system 100 similarly debits the correspondingamount of rewards points from the customer's rewards account balance. Inother arrangements, the interaction indication is received when thecustomer makes a purchase using their payment card 108 which earns thecustomer rewards points. In this case, the system 100 (e.g., providercomputing system 118) is capable of crediting the corresponding amountof rewards points to the customer's rewards account balance.

Customer interaction activity is analyzed at 304. In some arrangements,the customer interaction activity information is analyzed by theengagement rating circuit 130 of the provider computing system 118. Theengagement rating circuit 130, as noted above, analyzes the activity ofthe customer in relation to the rewards system. The engagement ratingcircuit 130 determines what type of interaction the customer had withthe previously sent rewards engagement message. Depending on the type ofinteraction, the rewards engagement score may go up or down. Theengagement rating circuit 130 takes into account the interactionactivity received from the customer (e.g., from customer device 112).

For example, if the customer interacted with the system to dismiss theprevious rewards engagement message, the rewards engagement score willlikely be a lower rewards engagement score than previously given to thecustomer due to the dismissal of the message. As another example, if thecustomer interacted with the system to click on a link in the message toview a video about how to earn or burn more rewards points, the rewardsengagement score will likely be a higher rewards engagement score thanpreviously given to the customer due to the customer's engagement withthe system via the informational video. A rewards engagement score isupdated based on the customer interaction activity at 306. In somearrangements, the rewards engagement score is generated by theengagement rating circuit 130 of the provider computing system 118.Based on the analysis performed at 304, the engagement rating circuit130 generates an updated rewards engagement score for the customer.

A rewards engagement message based on the customer interaction activityis generated at 308. In some arrangements, the rewards engagementmessage is generated by the messaging circuit 132 of the providercomputing system 118. The messaging circuit 132 receives the updatedrewards engagement score from the engagement rating circuit 130 anddetermines the type of updated message to send to the customer. Therewards engagement message is transmitted to the customer at 310. Themessaging circuit 132 transmits the rewards engagement message to thecustomer. In some arrangements, the updated rewards engagement messageis transmitted to the customer in various ways based on customerpreferences stored in the rewards database 136. In some arrangements,the messaging circuit 132 transmits the rewards engagement message usingthe previous channel through which a message was sent. In this way, themessaging circuit 132 is targeting the message to the customer in a waythat the customer has been prompted to interact with previously and assuch, is likely to get the customer to interact with again. The methodbegins again at 302 to continuously monitor the customer interactionactivity with the rewards engagement system 100.

Referring to FIGS. 4-6, graphical user interfaces displayed on thecustomer device 112 via the client application 148 are shown, accordingto example embodiments. Referring now to FIG. 4, an example screenshotof a client application interface of the customer device 112 associatedwith a customer is shown, according to an example embodiment. Theinterface 400 is indicative of a rewards burn opportunities interfacethe customer could receive. The interface 400 includes a notification410 notifying the customer that they currently have 50,000 rewardspoints available, a notification 412 that the customer can redeemrewards for travel, and a notification 414 that a link is provided thatthe customer can click to view rewards travel options. The interface 400further includes one or more selections with which the customer caninteract. For example, the selections can include a “Rewards Travel”selection 416 in the form of a link that the customer can click on toview rewards burn opportunities. In some embodiments, the customerreceives the notification based on the system 100 determining that thecustomer has not burned rewards points in a certain amount of time, thatthe customer has enough points for a particular rewards purchase, or thelike. The provider computing system 118 transmits the notificationinformation to the customer device 112 (e.g., to the client application148 running on the customer device 112, which displays the notificationinformation to the customer as the interface 400).

Referring now to FIG. 5, an example screenshot of a client applicationinterface of the customer device 112 associated with a customer isshown, according to an example embodiment. The interface 500 isindicative of a rewards earn opportunities interface the customer couldreceive. The interface 500 includes a notification 510 notifying thecustomer that they currently have 500 rewards points available, anotification 512 that the customer has not earned any points in the pasttwo months, and a notification 514 prompting the customer to click on alink to view opportunities to earn rewards points. The interface 500further includes one or more selections with which the customer caninteract. For example, the selections can include an “Earn Points”selection 516 in the form of a link that the customer can click on toview opportunities to earn points and/or to view information on how toearn rewards points. In some embodiments, the customer receives thenotification based on the system 100 determining that the customer hasnot earned rewards points in a certain amount of time, etc. The providercomputing system 118 transmits the notification information to thecustomer device 112 (e.g., to the client application 148 running on thecustomer device 112, which displays the notification information to thecustomer as the interface 500).

Referring now to FIG. 6, an example screenshot of a client applicationinterface of the customer device 112 associated with a customer isshown, according to an example embodiment. The interface 600 isindicative of a rewards incentive interface the customer could receive.The interface 600 includes a notification 610 notifying the customerthat they have been selected to receive 5,000 points based on theirengagement with the rewards system, a notification 614 prompting thecustomer to click on a link to either add the points to their balance orredeem the points for merchandise. The interface 500 further includesone or more selections with which the customer can interact. Forexample, the selections can include an “Add Points to Rewards Account”selection 616 in the form of a link that the customer can click on toadd the points to their rewards account, and a “Redeem Points forMerchandise” selection 618 in the form of a link that the customer canclick on to view merchandise to purchase using redeemed rewards points.In some embodiments, the customer receives the notification based on thesystem 100 determining that the customer has been highly engaged withthe rewards system over a period of time, etc. The provider computingsystem 118 transmits the notification information to the customer device112 (e.g., to the client application 148 running on the customer device112, which displays the notification information to the customer as theinterface 600).

However, it should be understood that the interfaces and notificationsshown in FIGS. 4-6 are examples and that other notifications transmittedby the provider computing system 118 are contemplated by thisdisclosure. For example, in various arrangements, the provider computingsystem 118 instead transmits an email to the customer or a text messageto the customer device 112. Furthermore, in other embodiments, thenotification includes different or additional information. As anexample, the notification includes information on the customer's totalrewards balance, other ads for items that the customer can redeem therewards balance for (e.g., determined based on the customer's rewardsredemption history, determined based on the redemption histories ofother customers similar to the customer), and so on.

Referring to FIGS. 7-8, graphical user interfaces displayed on thecustomer device 112 via a provider portal are shown, according toexample embodiments. More specifically, FIGS. 7-8 depict examplescreenshots on the display 144 of the customer device 112 includingrewards banners generated based on the customer's rewards systemengagement. To begin with, FIG. 7 shows a website interface 700. Websiteinterface 700 may be indicative of a display generated based oninformation that the customer has not earned rewards point in a certainperiod of time such that rewards earning opportunities are presented.The website interface 700 includes rewards account information 702 forthe customer, for example, showing the customer's accounts and thebalance in each of the accounts. The information 702 includes rewardsbalance 706, including the rewards account balance and correspondingcash value, and points earned information 714, including transactionnames, respective points earned, and dates. The website interface 700also includes a rewards banner 708, which indicates that the customercan select options 710 or 712 on the banner 708 to either visit therewards store or view how to earn more rewards points. In variousembodiments, in response to selecting an option 710, 712 on the rewardsbanner 708, a rewards functionality is activated. Accordingly, thecustomer is redirected to another screen allowing the customer to viewrewards merchandise, rewards information, etc. The customer can alsoselection back to main menu option 716 and more accounts option 718.

Referring to FIG. 8, the website interface 800 includes rewards accountinformation 802 for the customer, for example, showing the customer'saccounts and the balance in each of the accounts. Website interface 800may be indicative of a display generated based on information that thecustomer has not redeemed their rewards points in a certain period oftime such that rewards burning opportunities are presented. Theinformation 802 includes rewards balance 806, including the rewardsaccount balance and corresponding cash value, and points earnedinformation 814, including transaction names, respective points earned,and dates. The website interface 800 also includes a rewards banner 708,which indicates that the customer can select options 810 or 812 on thebanner 808 to either redeem points for travel or view rewards trippackages. In various embodiments, in response to selecting an option810, 812 on the rewards banner 808, a rewards functionality isactivated. Accordingly, the customer is redirected to another screenallowing the customer to view rewards merchandise, rewards information,etc. The customer can also selection back to main menu option 816 andmore accounts option 818.

Furthermore, those of skill in the art will appreciate that FIGS. 7-8are meant to be illustrative, rather than limiting. For example, inother embodiments, the interfaces are configured differently, such asincluding a different number, order, or type of rewards servicesselections. As another example, in other embodiments, the rewards banneris displayed differently, such as displayed as a pop-up notificationtriggered, for example, when the customer selects a selectionredirecting the customer to view account balances or rewardsinformation.

The arrangements described herein have been described with reference todrawings. The drawings illustrate certain details of specificarrangements that implement the systems, methods and programs describedherein. However, describing the arrangements with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured toexecute the functions described herein. In some arrangements, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network interfaces, peripheraldevices, input devices, output devices, sensors, etc. In somearrangements, a circuit may take the form of one or more analogcircuits, electronic circuits (e.g., integrated circuits (IC), discretecircuits, system on a chip (SOCs) circuits, etc.), telecommunicationcircuits, hybrid circuits, and any other type of “circuit.” In thisregard, the “circuit” may include any type of component foraccomplishing or facilitating achievement of the operations describedherein. For example, a circuit as described herein may include one ormore transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR,etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on).

The “circuit” may also include one or more processors communicativelycoupled to one or more memory or memory devices. In this regard, the oneor more processors may execute instructions stored in the memory or mayexecute instructions otherwise accessible to the one or more processors.In some arrangements, the one or more processors may be embodied invarious ways. The one or more processors may be constructed in a mannersufficient to perform at least the operations described herein. In somearrangements, the one or more processors may be shared by multiplecircuits (e.g., circuit A and circuit B may comprise or otherwise sharethe same processor which, in some example arrangements, may executeinstructions stored, or otherwise accessed, via different areas ofmemory). Alternatively, or additionally, the one or more processors maybe structured to perform or otherwise execute certain operationsindependent of one or more co-processors. In other example arrangements,two or more processors may be coupled via a bus to enable independent,parallel, pipelined, or multi-threaded instruction execution. Eachprocessor may be implemented as one or more general-purpose processors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs), or other suitableelectronic data processing components structured to execute instructionsprovided by memory. The one or more processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor, etc.),microprocessor, etc. In some arrangements, the one or more processorsmay be external to the apparatus, for example the one or more processorsmay be a remote processor (e.g., a cloud based processor).Alternatively, or additionally, the one or more processors may beinternal and/or local to the apparatus. In this regard, a given circuitor components thereof may be disposed locally (e.g., as part of a localserver, a local computing system, etc.) or remotely (e.g., as part of aremote server such as a cloud based server). To that end, a “circuit” asdescribed herein may include components that are distributed across oneor more locations.

An exemplary system for implementing the overall system or portions ofthe arrangements might include a general purpose computing computers inthe form of computers, including a processing unit, a system memory, anda system bus that couples various system components including the systemmemory to the processing unit. Each memory device may includenon-transient volatile storage media, non-volatile storage media,non-transitory storage media (e.g., one or more volatile and/ornon-volatile memories), etc. In some arrangements, the non-volatilemedia may take the form of ROM, flash memory (e.g., flash memory such asNAND, 3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM, magnetic storage, harddiscs, optical discs, etc. In other arrangements, the volatile storagemedia may take the form of RAM, TRAM, ZRAM, etc. Combinations of theabove are also included within the scope of machine-readable media. Inthis regard, machine-executable instructions comprise, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions. Each respective memory devicemay be operable to maintain or otherwise store information relating tothe operations performed by one or more associated circuits, includingprocessor instructions and related data (e.g., database components,object code components, script components, etc.), in accordance with theexample arrangements described herein.

It should also be noted that the term “input devices,” as describedherein, may include any type of input device including, but not limitedto, a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. Comparatively, the term “output device,”as described herein, may include any type of output device including,but not limited to, a computer monitor, printer, facsimile machine, orother output devices performing a similar function.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative arrangements.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of arrangements has been presented forpurposes of illustration and description. It is not intended to beexhaustive or to limit the disclosure to the precise form disclosed, andmodifications and variations are possible in light of the aboveteachings or may be acquired from this disclosure. The arrangements werechosen and described in order to explain the principals of thedisclosure and its practical application to enable one skilled in theart to utilize the various arrangements and with various modificationsas are suited to the particular use contemplated. Other substitutions,modifications, changes and omissions may be made in the design,operating conditions and arrangement of the arrangements withoutdeparting from the scope of the present disclosure as expressed in theappended claims.

What is claimed is:
 1. A method comprising: establishing, by a providercomputing system, an application programming interface with a clientapplication installed on a user device to enable communication betweenthe provider computing system and the client application; receiving, bythe provider computing system, from the client application via theapplication programming interface, rewards activity informationassociated with a rewards account associated with the user device andmaintained by the provider computing system; receiving, by the providercomputing system, from the client application or from a merchant device,payment card information transmitted by the client application to themerchant device, the payment card information associated with a paymentaccount associated with a user of the user device; generating, by theprovider computing system, a first rewards engagement score for therewards account based on the rewards activity information and thepayment card information; transmitting, by the provider computingsystem, a first push notification to the client application via theapplication programming interface, the first push notificationcomprising a first rewards engagement message for display in a firstgraphical user interface of the client application, the first rewardsengagement message based on the first rewards engagement score;receiving, by the provider computing system, from the client applicationvia the application programming interface, a first interactionindication corresponding to a first interaction with the first graphicaluser interface; determining, by the provider computing system, from thefirst interaction indication, that the first interaction is a dismissalof the first rewards engagement message displayed on the first graphicaluser interface of the client application; generating, by the providercomputing system, a second rewards engagement score for the rewardsaccount based on the dismissal of the first rewards engagement message;transmitting, by the provider computing system, a second pushnotification to the client application via the application programminginterface, the second push notification comprising a second rewardsengagement message for display in a second graphical user interface ofthe client application, the second rewards engagement message based onthe second rewards engagement score; receiving, by the providercomputing system, from the client application via the applicationprogramming interface, a second interaction indication corresponding toa second interaction with the second graphical user interface;determining, by the provider computing system, from the secondinteraction indication, that the second interaction was a click of alink in the second rewards engagement message; generating, by theprovider computing system, a third rewards engagement score for therewards account based on the click of the link; transmitting, by theprovider computing system, a third push notification to the clientapplication via the application programming interface, the third pushnotification comprising a third rewards engagement message for displayin a third graphical user interface, the third rewards engagementmessage based on the third rewards engagement score; assigning, by theprovider computing system, redemption points to the rewards accountbased on the third rewards engagement score; determining, by theprovider computing system, based on information received from themerchant device, that the redemption points were not redeemed within apredetermined amount of time; and transmitting, by the providercomputing system, via the application programming interface, redemptioninformation for display in a fourth graphical user interface of theclient application to indicate that the redemption points assigned tothe rewards account were not redeemed.
 2. The method of claim 1, furthercomprising: receiving, by the provider computing system, a rewardsredemption indication from the user device in response to the thirdrewards engagement message; and debiting, by the provider computingsystem, the redemption points from the rewards account maintained by theprovider computing system and associated with the user device.
 3. Themethod of claim 1, further comprising: receiving, by the providercomputing system, a payment card indication from the user device inresponse to the third rewards engagement message, the payment cardindication relating to a purchase made by the user device using apayment card associated with the rewards account; and crediting, by theprovider computing system, an amount of the redemption points to therewards account maintained by the provider computing system andassociated with the user device.
 4. The method of claim 1, wherein thesecond rewards engagement score is lower than the first rewardsengagement score.
 5. The method of claim 1, wherein the secondinteraction indication is a rewards points redemption and the thirdrewards engagement score is higher than the second rewards engagementscore.
 6. The method of claim 1, wherein the third rewards engagementmessage includes an indication of incentive rewards points added to therewards account in response to the second interaction indication.
 7. Themethod of claim 1, wherein the first, second, or third rewardsengagement message is transmitted as a banner on a website portal of theprovider computing system, an email, or a text message.
 8. The method ofclaim 1, wherein the first, second, or third rewards engagement messageincludes an advertisement for the user device to engage in a rewardspoints earning activity.
 9. The method of claim 1, wherein the first,second, or third rewards engagement message includes an advertisementfor the user device to engage in a rewards points burning activity. 10.A provider computing system associated with a provider, the providercomputing system comprising: a network interface structured tofacilitate data communication via a network; an accounts databasestructured to store information associated with a payment accountassociated with a user device; a rewards database structured to storeinformation associated with a rewards account associated with the userdevice; a processing circuit comprising a processor and memory, theprocessing circuit structured to: establish an application programminginterface with a client application installed on the user device toenable communication between the provider computing system and theclient application; receive, from the client application via theapplication programming interface, rewards activity informationassociated with the rewards account associated with the user device andmaintained by the provider; receive, from the client application or froma merchant device, payment card information transmitted by the clientapplication to the merchant device, the payment card informationassociated with the payment account associated with a user of the userdevice; generate a first rewards engagement score for the rewardsaccount based on the rewards activity information and the payment cardinformation; transmit a first push notification to the clientapplication via the application programming interface, the first pushnotification comprising a first rewards engagement message for displayin a first graphical user interface of the client application, the firstrewards engagement message based on the first rewards engagement score;receive from the user device from the client application via theapplication programming interface, a first interaction indicationcorresponding to a first interaction with the first graphical userinterface; determine, from the first interaction indication, that thefirst interaction is a dismissal of the first rewards engagement messagedisplayed on the first graphical user interface of the clientapplication; generate, a second rewards engagement score for the rewardsaccount based on the dismissal of the first rewards engagement message;transmit, a second push notification to the client application via theapplication programming interface, the second push notificationcomprising a second rewards engagement message for display in a secondgraphical user interface of the client application, the second rewardsengagement message based on the second rewards engagement score;receive, from the client application via the application programminginterface, a second interaction indication corresponding to a secondinteraction with the second graphical user interface; determine from thesecond interaction indication, that the second interaction was a clickof a link in the second rewards engagement message; generate a thirdrewards engagement score for the rewards account based on the click ofthe link; transmit the a third push notification to the clientapplication via the application programming interface, the third pushnotification comprising a third rewards engagement message for displayin a third graphical user interface, the third rewards engagementmessage based on the third rewards engagement score; assign redemptionpoints to the rewards account based on the third rewards engagementscore; determine, based on information received from the merchantdevice, that the redemption points were not redeemed within apredetermined amount of time; and transmit, via the applicationprogramming interface, redemption information for display in a fourthgraphical user interface of the client application to indicate that theredemption points assigned to the rewards account were not redeemed. 11.The provider computing system of claim 10, wherein the processingcircuit is further configured to: receive a rewards redemptionindication from the user device in response to the third rewardsengagement message; and debit the redemption points from the rewardsaccount maintained by the provider and associated with the user device.12. The provider computing system of claim 10, wherein the processingcircuit is further configured to: receive a payment card indication fromthe user device in response to the third rewards engagement message, thepayment card indication relating to a purchase made by the user deviceusing payment card associated with the rewards account; and credit theredemption points to the rewards account maintained by the provider andassociated with the user device.
 13. The provider computing system ofclaim 10, wherein the second rewards engagement score is lower than thefirst rewards engagement score.
 14. The provider computing system ofclaim 10, wherein the second interaction indication is a rewards pointsredemption and the third rewards engagement score is higher than thesecond rewards engagement score.
 15. The provider computing system ofclaim 10, wherein the third rewards engagement message is transmitted asa banner on a website portal of the provider, an email, or a textmessage.
 16. The provider computing system of claim 10, wherein thefirst, second, or third rewards engagement message includes anadvertisement for the user device to engage in a rewards points earningactivity.
 17. The provider computing system of claim 10, wherein thefirst, second, or third rewards engagement message includes anadvertisement for the user device to engage in a rewards points burningactivity.
 18. A user device comprising: a network circuit structured tocommunicate data to and from an application programming interface of aprovider computing system associated with a provider of a rewardsaccount associated with the user device and maintained by the providercomputing system; an input/output device structured to exchange datawith the user device; a client application installed on the user device;and a processing circuit comprising a processor and memory, theprocessing circuit structured to: transmit, via the network circuit tothe provider computing system, payment card information associated witha payment account associated with a user of the user device; transmit,via the network circuit to the provider computing system, rewardsactivity information associated with the rewards account; receive, viathe network circuit, for display by the client application, a first pushnotification for display in a first graphical user interface of theclient application, the first push notification comprising a firstrewards engagement message generated by the provider computing systembased on the rewards activity information and the payment cardinformation, the first graphical user interface enabling the user deviceto receive, via the input/output device, selections or dismissals of thefirst rewards engagement message; receive a first input from the userdevice via the input/output device, the first input indicating adismissal of the first rewards engagement message; transmit, via thenetwork circuit, a first indication of the dismissal, to the providercomputing system; and receive, via the network circuit, a second pushnotification for display in a second graphical user interface of theclient application, the second push notification comprising a secondrewards engagement message to indicate a change in the rewards account,the second graphical user interface enabling the user device to receive,via the input/output device, selections or dismissals of the secondrewards engagement message; receive a second input from the user devicevia the input/output device, the second input indicating a selection ofthe second rewards engagement message; transmit, via the networkcircuit, a second indication of the selection, to the provider computingsystem; receive a third push notification comprising a third rewardsengagement message for display in a third graphical user interface ofthe client application, the third rewards engagement message indicatingredemption points assigned to the rewards account based on theselection; and receive, via the network circuit, redemption informationfor display in a fourth graphical user interface of the clientapplication, the redemption information indicating that the redemptionpoints assigned to the rewards account were not redeemed.
 19. The userdevice of claim 18, wherein the processing circuit is further configuredto: receive a rewards redemption from the input/output device inresponse to the third rewards engagement message; and transmit therewards redemption to the provider computing system.
 20. The user deviceof claim 18, wherein the processing circuit is further configured to:receive a payment card from the input/output device in response to thefirst, second, or third rewards engagement messages, the payment cardrelating to a purchase made by the user device using the payment cardassociated with the one or more rewards accounts; and transmit thepayment card to the provider computing system.
 21. The user device ofclaim 18, wherein the first, second, or third rewards engagementmessages are received and displayed as a banner on a website portal ofthe provider, an email, or a text message.
 22. The user device of claim18, wherein first, second, or third rewards engagement messages includean advertisement for the user device to engage in a rewards pointsearning activity.
 23. The user device of claim 18, wherein the first,second, or third rewards engagement messages include an advertisementfor the user device to engage in a rewards points burning activity.